Systems and methods for network-based identification of priority services

ABSTRACT

A network device may receive, from a user device, a call associated with a telephone number, where the call is intended for a priority service associated with the telephone number. The network device may identify the call as a priority call based on the telephone number associated with the call, and may determine that a network overload condition exists. The network device may associate a priority tag with the call based on identifying the call as a priority call. The network device may cause the call to be provided preferential treatment, while the call is transmitted for the priority service during the network overload condition, based on the priority tag.

BACKGROUND

A network, such as a fourth generation (4G) network or a fifthgeneration (5G) network, may experience a network overload conditionwhen particular events (e.g., floods, earthquakes, hurricanes,blizzards, terrorist attacks, and/or the like) occur.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1J are diagrams of an example associated with network-basedidentification of priority services.

FIGS. 2 and 3 are diagrams of example environments in which systemsand/or methods described herein may be implemented.

FIG. 4 is a diagram of example components of one or more devices ofFIGS. 2 and 3 .

FIG. 5 is a flowchart of an example process for network-basedidentification of priority services.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Currently, some calls that are high priority in nature (e.g., a 988suicide hotline call, a call to a local police department, a call to alocal fire department, and/or the like), are not identified at thenetwork level as high priority calls. When these calls are initiated byusers on user equipment (UE) during a network overload condition, anetwork may most likely drop these types of calls regardless of theiractual priority because they are not designated as prioritized at anetwork level. The network fails to identify such priority calls as highpriority calls since the network currently does not provide anend-to-end priority call identification mechanism during networkoverload conditions. Thus, the network fails to ensure that the prioritycalls are identified and handled as high priority calls when the networkis in an overload condition. Thus, lack of existing mechanisms forhandling priority calls during a network overload condition cause thenetwork to excessively consume computing resources (e.g., processingresources, memory resources, communication resources, and/or the like),networking resources, and/or other resources associated with causinguser devices to place priority calls multiple times before connecting topriority services, handling multiple priority calls from the same userdevices, handling dropped priority calls, failing to connect prioritycalls to priority services, and/or the like.

Some implementations described herein provide a network device (e.g., aproxy call session control function (P-CSCF)) that providesnetwork-based identification of priority services. For example, theP-CSCF may receive, from a user device, a call associated with atelephone number, where the call is intended for a priority serviceassociated with the telephone number. The P-CSCF may identify the callas a priority call based on the telephone number associated with thecall, and may determine that a network overload condition exists. TheP-CSCF may associate a priority tag with the call based on identifyingthe call as a priority call. The P-CSCF may cause the call to beprovided preferential treatment, while the call is transmitted for thepriority service during the network overload condition, based on thepriority tag, in contrast to untagged calls that do not receive thispreferential treatment.

In this way, the P-CSCF provides network-based identification ofpriority services. For example, the P-CSCF may ensure that a prioritycall (e.g., a 988 suicide hotline call, a call to a local policedepartment, a call to a local fire department, and/or the like) has anincreased probability of call completion and is not dropped when anetwork experiences an overload condition. Thus, the P-CSCF may conservecomputing resources, networking resources, and/or other resources thatwould otherwise have been consumed by causing user devices to placepriority calls multiple times before connecting to priority services,handling multiple priority calls from the same user devices, handlingdropped priority calls, failing to connect priority calls to priorityservices, and/or the like.

FIGS. 1A-1J are diagrams of an example 100 associated with network-basedidentification of priority services. As shown in FIGS. 1A-1J, example100 includes a user device 105, a RAN 110, and a core network 115. Thecore network 115 may include a P-CSCF 120, a serving gateway (SGW) or auser plane function (UPF), a policy and charging rules function (PCRF)or a policy control function (PCF), a home subscriber server (HSS), aninterrogating or serving CSCF (I/S-CSCF), a telephony application server(TAS), and an online charging system (OCS)/charging collection function(CCF). Further details of the user device 105, the RAN 110, the corenetwork 115, the P-CSCF 120, the network analytics engine, the contentserver, the PCRF, the PCF, the HSS, the I/S-CSCF, the TAS, and theOCS/CCF are provided elsewhere herein. Although only a single userdevice 105 and RAN 110 are depicted in FIG. 1A, in some implementationsmultiple user devices 105 and RANs 110 may be associated with the corenetwork 115. Furthermore, the core network 115 shown in FIGS. 1A, 1B,and 1G-1J includes network devices associated with a 4G network, and thecore network 115 shown in FIGS. 1C and 1D includes network devicesassociated with a 5G network.

As shown in FIG. 1A, and by reference number 125, the user device 105may generate a call to a telephone number. For example, a user mayutilize the user device 105 to input digits of the telephone number, andthe user device 105 may generate the call to the telephone number basedon the inputted digits. In some implementations, the telephone numbermay be associated with a priority service, such as a suicide hotline, apolice department, a fire department, a hospital, a poison controlservice, and/or the like. Although implementations described hereinrelate to the P-CSCF 120 performing functions, in other implementations,other network devices of the core network 115 may perform one or more ofthe functions described as being performed by the P-CSCF 120.

As further shown in FIG. 1A, and by reference number 130, the P-CSCF 120may receive the call during a network overload condition. For example,the P-CSCF 120 may determine that a network overload condition exists inthe core network 115 based on a traffic load associated with the corenetwork 115 and/or the P-CSCF 120, an available bandwidth associatedwith the core network 115 and/or the P-CSCF 120, an indication ofoccurrence of a particular event, and/or the like. The particular eventmay include a man-made disaster (e.g., a plane crash, a ship sinking, abuilding explosion, a nuclear meltdown, a chemical spill, and/or thelike), a natural disaster (e.g., a flood, an earthquake, a wildfire, ahurricane, a blizzard, and/or the like), a terrorist attack, and/or thelike. When the P-CSCF 120 determines that the network overload conditionexists, the P-CSCF 120 may determine whether the call is received duringthe network overload condition. If the call is not received during thenetwork overload condition, the P-CSCF 120 may process the callaccording to typical processing procedures. If the call is receivedduring the network overload condition, the P-CSCF 120 may process thecall as described below.

As shown in FIG. 1B, and by reference number 135, the P-CSCF 120 mayidentify the call as a priority call based on a call identifier (e.g.,the telephone number) associated with the call. For example, the P-CSCF120 may identify the call as a priority call by comparing the callidentifier (e.g., digits of the telephone number) with a list of callidentifiers (e.g., telephone numbers) associated with priority services.When the call identifier (e.g., the digits of the telephone number)match a call identifier (e.g., digits of a telephone number) in the listof call identifiers (e.g., telephone numbers) associated with priorityservices, the P-CSCF 120 may identify the call as a priority call. Whenthe call identifier (e.g., the digits of the telephone number) fail tomatch a call identifier (e.g., digits of a telephone number) in the listof call identifiers (e.g., telephone numbers) associated with priorityservices, the P-CSCF 120 may not identify the call as a priority call.In some implementations, the list of call identifiers (e.g., telephonenumbers) associated with priority services may include call identifiers(e.g., telephone numbers) associated with a suicide hotline, a policedepartment, a fire department, a hospital, a poison control service,and/or the like.

As further shown in FIG. 1B, and by reference number 140, the P-CSCF 120may associate a priority tag with the call. For example, the P-CSCF 120may associate the priority tag with the call based on identifying thecall as a priority call and based on determining that the networkoverload condition exists. When the call is not identified as a prioritycall or a network overload condition does not exist, the P-CSCF 120 maynot associate the priority tag with the call. The priority tag mayindicate that the call is a priority call to subsequent network devicesin a path of call delivery. In some implementations, the priority tagmay include a reservation priority attribute-value pair (AVP) and amultimedia priority service AVP, a session initiation protocol (SIP)resource priority header, a session priority AVP, and/or the like.

The P-CSCF 120 may associate the priority tag with the call so that allsubsequent steps in a delivery setup of the call may receivepreferential treatment during the network overload condition. Allsubsequent call steps for different protocols may include priority tagsindicating that the call is a priority call. The subsequent networkdevices may identify the call as a priority call, may mark the callaccordingly (e.g., based on the different protocols), and may providepreferential treatment to the call during the network overloadcondition. For example, the P-CSCF 120 may utilize the reservationpriority AVP and the multimedia priority service AVP, as the prioritytag, to indicate the priority of the call to the PCRF via an Rxinterface between the P-CSCF 120 and the PCRF. The P-CSCF 120 mayutilize the reservation priority AVP and the multimedia priority serviceAVP, as the priority tag, to indicate the priority of the call to theSGW via a Gm interface between the P-CSCF 120 and the SGW. The P-CSCF120 may utilize the reservation priority AVP and the multimedia priorityservice AVP, as the priority tag, to indicate the priority of the callto the I/S-CSCF via an Mw interface between the P-CSCF 120 and theI/S-CSCF. The I/S-CSCF may utilize the SIP resource priority header, asthe priority tag, to indicate the priority of the call to the TAS via anISC interface between the I/S-CSCF and the TAS. The I/S-CSCF may utilizethe session priority AVP, as the priority tag, to indicate the priorityof the call to the HSS via a Cx interface between the I/S-CSCF and theHSS. The HSS may utilize the session priority AVP, as the priority tag,to indicate the priority of the call to the TAS via an Sh interfacebetween the HSS and the TAS. The TAS may utilize the session priorityAVP, as the priority tag, to indicate the priority of the call to theOCS/CCF via an Ro interface between the TAS and the OCS/CCF.

As further shown in FIG. 1B, and by reference number 145, the P-CSCF 120may cause the call to be provided preferential treatment during thenetwork overload condition based on the priority tag. For example, whencausing the call to be provided preferential treatment during thenetwork overload condition based on the priority tag, the P-CSCF 120 maycause, based on the priority tag, one or more other network devices(e.g., the SGW, the PCRF, the I/S-CSCF, the HSS, the TAS, the OCS/CCF,and/or the like) to identify the call as a priority call and to providepreferential treatment for the call during the network overloadcondition. In some implementations, a connection may be establishedbetween the user device 105 and a priority service (e.g., a calldestination) associated with the telephone number based on causing thecall to be provided preferential treatment during the network overloadcondition. In some implementations, all subsequent call steps fordifferent protocols may include priority tags indicating that the callis a priority call. The subsequent network devices may identify the callas a priority call, may mark the call accordingly (e.g., based on thedifferent protocols), and may provide preferential treatment to the callduring the network overload condition.

As shown in FIG. 1C, and by reference number 150, the user device maygenerate a call to a telephone number. For example, a user may utilizethe user device 105 to input digits of the telephone number, and theuser device 105 may generate the call to the telephone number based onthe inputted digits. In some implementations, the telephone number maybe associated with a priority service, such as a suicide hotline, apolice department, a fire department, a hospital, a poison controlservice, and/or the like.

As further shown in FIG. 1C, and by reference number 155, the P-CSCF 120may receive the call during a network overload condition. For example,the P-CSCF 120 may determine that a network overload condition exists inthe core network 115 based on a traffic load associated with the corenetwork 115 and/or the P-CSCF 120, an available bandwidth associatedwith the core network 115 and/or the P-CSCF 120, an indication ofoccurrence of a particular event, and/or the like. The particular eventmay include a man-made disaster, a natural disaster, a terrorist attack,and/or the like. When the P-CSCF 120 determines that the networkoverload condition exists, the P-CSCF 120 may determine whether the callis received during the network overload condition. If the call is notreceived during the network overload condition, the P-CSCF 120 mayprocess the call according to typical processing procedures. If the callis received during the network overload condition, the P-CSCF 120 mayprocess the call as described below.

As shown in FIG. 1D, and by reference number 160, the P-CSCF 120 mayidentify the call as a priority call based on a call identifier (e.g.,the telephone number) associated with the call. For example, the P-CSCF120 may identify the call as a priority call by comparing the callidentifier (e.g., digits of the telephone number) with the list of callidentifiers (e.g., telephone numbers) associated with priority services.When the call identifier (e.g., the digits of the telephone number)match a call identifier (e.g., digits of a telephone number) in the listof call identifiers (e.g., telephone numbers) associated with priorityservices, the P-CSCF 120 may identify the call as a priority call. Whenthe call identifier (e.g., the digits of the telephone number) fail tomatch a call identifier (e.g., digits of a telephone number) in the listof call identifiers (e.g., telephone numbers) associated with priorityservices, the P-CSCF 120 may not identify the call as a priority call.

As further shown in FIG. 1D, and by reference number 165, the P-CSCF 120may associate a priority tag with the call. For example, the P-CSCF 120may associate the priority tag with the call based on identifying thecall as a priority call and based on determining that the networkoverload condition exists. When the call is not identified as a prioritycall or a network overload condition does not exist, the P-CSCF 120 maynot associate the priority tag with the call. The priority tag mayindicate that the call is a priority call to subsequent network devicesin a path of call delivery. For example, the P-CSCF 120 may utilize thereservation priority AVP and the multimedia priority service AVP, as thepriority tag, to indicate the priority of the call to the PCF via an Rxinterface between the P-CSCF 120 and the PCF. The P-CSCF 120 may utilizethe reservation priority AVP and the multimedia priority service AVP, asthe priority tag, to indicate the priority of the call to the UPF via aGm interface between the P-CSCF 120 and the UPF. The indications of thepriority of the call, via the other interfaces depicted in FIG. 1D, aredescribed above in connection with FIG. 1B.

As further shown in FIG. 1D, and by reference number 170, the P-CSCF 120may cause the call to be provided preferential treatment during thenetwork overload condition based on the priority tag. For example, whencausing the call to be provided preferential treatment during thenetwork overload condition based on the priority tag, the P-CSCF 120 maycause, based on the priority tag, one or more other network devices(e.g., the UPF, the PCF, the I/S-CSCF, the HSS, the TAS, the OCS/CCF,and/or the like) to identify the call as a priority call and to providepreferential treatment for the call during the network overloadcondition. In some implementations, a connection may be establishedbetween the user device 105 and a priority service (e.g., a calldestination) associated with the telephone number based on causing thecall to be provided preferential treatment during the network overloadcondition. In some implementations, all subsequent call steps fordifferent protocols may include priority tags indicating that the callis a priority call. The subsequent network devices may identify the callas a priority call, may mark the call accordingly (e.g., based on thedifferent protocols), and may provide preferential treatment to the callduring the network overload condition.

FIGS. 1E and 1F are diagrams of mapping tables capable of being utilizedby the P-CSCF 120. As shown in the top mapping table of FIG. 1E, a SIPresource priority header (RPH) may be formatted to include emergencymedical services (EMS) priorities (e.g., National Alliance on MentalIllness (NAMI) 988 (ems.1), police (ems.2), fire (ems.3), and poisoncontrol (ems.x)), and/or the like. As shown in the bottom mapping tableof FIG. 1E, user interactions (e.g., dialed telephone numbers) may bemapped to invocation methods and information included in a SIP inviteRPH. As shown, a user interaction of “988” may be mapped to a suicidehotline and a SIP invite RPH that includes ems.1; a user interaction of“xxx-xxx-xxxx” may be mapped to a police station and a SIP invite RPHthat includes ems.2; a user interaction of “xxx-xxx-xxxx” may be mappedto another priority service and a SIP invite RPH that includes ems.x;and/or the like. As shown in the mapping table of FIG. 1F, a sessionpriority AVP value may be mapped to a SIP RPH value and a reservationpriority AVP value. For example, a session priority AVP of “x” may bemapped to a SIP RPH value of “ems.0” and a reservation priority AVPvalue of “x”; a session priority AVP of “y” may be mapped to a SIP RPHvalue of “ems.x” and a reservation priority AVP value of “y”; and/or thelike.

FIGS. 1G-1J are call flow diagrams associated with network-basedidentification of priority services. As shown at step 1 of FIG. 1G, afirst user device 105-1 may generate an invite (e.g., based on a mentalhealth telephone number, such as 988) destined for a priority serviceprovided by a second user device 105-2, and may provide the invite to afirst P-CSCF 120-1. The first P-CSCF 120-1 may evaluate a dial string(e.g., digits) associated with the telephone number and may insert anRPH with a priority (e.g., ems.x) into the invite. The first P-CSCF120-1 may provide an AA request (AAR) command, with the priorityindicated by a new reservation priority value, to a first PCRF (e.g.,PCRF 1). The first PCRF may provide a re-auth request (RAR) command to afirst PGW (e.g., PGW 1), and the first PGW may acknowledge receipt ofthe RAR command via a re-auth acknowledgement (RAA) command.

As shown at step 2 of FIG. 1G, the first P-CSCF 120-1 may provide theinvite (e.g., identifying the second user device 105-2 and the priority)to a first S-CSCF (e.g., S-CSCF 1). As shown at steps 3 and 4, the firstS-CSCF may forward the invite to a first TAS (e.g., TAS 1), and thefirst TAS may acknowledge receipt of the invite from the first S-CSCF.As shown at step 5 of FIG. 1G, the first S-CSCF may provide the inviteto a first I-CSCF (e.g., I-CSCF 1). The first I-CSCF may utilize alocation information request (LIR) command and answer (LIA) to notifythe HS S of the priority associated with the invite. As shown at step 6of FIG. 1G, the first I-CSCF may provide the invite to a second S-CSCF(e.g., S-CSCF 2). As shown at steps 7 and 8, the second S-CSCF mayforward the invite to a second TAS (e.g., TAS 2), and the second TAS mayacknowledge receipt of the invite from the second S-CSCF.

As shown at steps 9 and 10 of FIG. 1H, the second S-CSCF may forward theinvite to a second SGW (e.g., SGW 2), and the second SGW may acknowledgereceipt of the invite from the second S-CSCF. As shown at step 11, thesecond S-CSCF may provide the invite to a second P-CSCF 120-2. Thesecond P-CSCF 120-2 may apply the RP header to an Rx interface, and mayprovide an AAR command, with the priority indicated by a new reservationpriority value, to a second PGW (e.g., PGW 2). The second PGW mayprovide an RAR command to a second PCRF (e.g., PCRF 2), and the secondPCRF may acknowledge receipt of the RAR command via an RAA commandprovided to the second P-CSCF 120-2. As shown at step 12 of FIG. 1H, thesecond P-CSCF 120-2 may provide the invite to the second user device105-2, via the second PGW. As shown at step 13, the second user device105-2 may provide, in response to the invite, a ringing response to thesecond P-CSCF 120-2, via the second PGW. The second P-CSCF 120-2 mayinsert the RP header in the ringing response. As shown at step 14 ofFIG. 1H, the second P-CSCF 120-2 may provide the ringing response (e.g.,with the inserted RP header) to the second S-CSCF. As shown at step 15,the second S-CSCF may provide the ringing response to the second SGW.

As shown at step 16 of FIG. 1I, the second SGW may provide anacknowledgement of the ringing response to the second S-CSCF. As shownat steps 17 and 18, the second S-CSCF may forward the ringing responseto the second TAS, and the second TAS may acknowledge receipt of theringing response from the second S-CSCF. As shown at step 19, the secondS-CSCF may forward the ringing response to the first S-CSCF, via thefirst I-CSCF. As shown at steps 20 and 21, the first S-CSCF may forwardthe ringing response to the first TAS, and the first TAS may acknowledgereceipt of the ringing response from the first S-CSCF. As shown at steps22 and 23 of FIG. 1I, the first S-CSCF may forward the ringing responseto the first P-CSCF 120-1, and the first P-CSCF 120-1 may forward theringing response to the first user device 105-1, via the first PGW.Steps 24-39, associated with acknowledgement of the ringing response andsetting up the call between the first user device 105-1 and the seconduser device 105-2, are not shown in FIG. 1I for ease of explanation.

As shown at step 40 of FIG. 1I, the second user device 105-2 may providean answer (e.g., a 200 OK answer to the call) to the second P-CSCF120-2, via the second PGW. The second P-CSCF 120-2 may provide an AARcommand, with the priority indicated by a new reservation priorityvalue, to the second PCRF. The second PCRF may provide an RAR command tothe second PGW, and the second PGW may acknowledge receipt of the RARcommand via an RAA command provided to the second PCRF. The second PCRFmay provide an acknowledgement of the AAR command (e.g., an AAA) to thesecond P-CSCF 120-2. As shown at step 41, the second P-CSCF 120-2 mayprovide the answer to the second S-CSCF. As shown at steps 42 and 43,the second S-CSCF may forward the answer to the second SGW, and thesecond SGW may acknowledge receipt of the answer from the second S-CSCF.

As shown at steps 44 and 45 of FIG. 1J, the second S-CSCF may forwardthe answer to the second TAS, and the second TAS may acknowledge receiptof the answer from the second S-CSCF. As shown at step 46, the secondS-CSCF may forward the answer to the first S-CSCF, via the first I-CSCF.As shown at steps 47 and 48, the first S-CSCF may forward the answer tothe first TAS, and the first TAS may acknowledge receipt of the answerfrom the first S-CSCF. As shown at step 49 of FIG. 1J, the first S-CSCFmay forward the answer to the first P-CSCF 120-1. The first P-CSCF 120-1may provide an AAR command, with the priority indicated by a newreservation priority value, to the first PCRF. The first PCRF mayprovide an RAR command to the first PGW, and the first PGW mayacknowledge receipt of the RAR command via an RAA command provided tothe first PCRF. As shown at step 50, the first P-CSCF 120-1 may forwardthe answer to the first user device 105-1, via the first PGW. At thispoint, a dedicated bearer may be established for voice and/or videobetween the first user device 105-1 and the second user device 105-2.

As shown at step 51 of FIG. 1J, the first user device 105-1 may providean acknowledgement (e.g., in response to establishment of the dedicatedbearer) to the first P-CSCF 120-1. As shown at step 52, the first P-CSCF120-1 may forward the acknowledgement to the first S-CSCF. As shown atsteps 53 and 54, the first S-CSCF may forward the acknowledgement to thefirst TAS, and the first TAS may acknowledge receipt of theacknowledgement from the first S-CSCF. As shown at step 55, the firstS-CSCF may forward the acknowledgement to the second S-CSCF. As shown atsteps 56 and 57, the second S-CSCF may forward the acknowledgement tothe second TAS, and the second TAS may acknowledge receipt of theacknowledgement from the second S-CSCF. As shown at steps 58 and 59, thesecond S-CSCF may forward the acknowledgement to the second SGW, and thesecond SGW may acknowledge receipt of the acknowledgement from thesecond S-CSCF. As shown at steps 60 and 61, the second S-CSCF mayforward the acknowledgement to the second P-CSCF 120-2, and the secondP-CSCF 120-2 may forward the acknowledgement to the second user device105-2, via the second PGW.

In this way, the P-CSCF 120 provides network-based identification ofpriority services. For example, the P-CSCF 120 may ensure that apriority call (e.g., a 988 suicide hotline call, a call to a localpolice department, a call to a local fire department, and/or the like)has an increased probability of call completion and is not dropped whena network experiences an overload condition. The P-CSCF 120 may ensurethat priority calls receive preferential treatment by the network duringa network overload condition. Therefore, the P-CSCF 120 may increasecall completion rates for any newly-defined priority calls. Thus, theP-CSCF 120 may conserve computing resources, networking resources,and/or other resources that would otherwise have been consumed bycausing user devices 105 to place priority calls multiple times beforeconnecting to priority services, handling multiple priority calls fromthe same user devices 105, handling dropped priority calls, failing toconnect priority calls to priority services, and/or the like.

As indicated above, FIGS. 1A-1J are provided as an example. Otherexamples may differ from what is described with regard to FIGS. 1A-1J.The number and arrangement of devices shown in FIGS. 1A-1J are providedas an example. In practice, there may be additional devices, fewerdevices, different devices, or differently arranged devices than thoseshown in FIGS. 1A-1J. Furthermore, two or more devices shown in FIGS.1A-1J may be implemented within a single device, or a single deviceshown in FIGS. 1A-1J may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) shown in FIGS. 1A-1J may perform one or more functionsdescribed as being performed by another set of devices shown in FIGS.1A-1J.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG. 2, the environment 200 may include the user device 105, the RAN 110, andthe core network 115. The core network 115 may include the P-CSCF 120, amobility management entity device (MME) 205, SGW 210, a PGW 215, a PCRF220, an OCS/CCF 225, a TAS 230, an I/S-CSCF 235, an HSS 240, anauthentication, authorization, and accounting server (AAA) 245, and anetwork 250. Devices of the environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

The user device 105 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information, such asinformation described herein. For example, the user device 105 caninclude a mobile phone (e.g., a smart phone or a radiotelephone), alaptop computer, a tablet computer, a desktop computer, a handheldcomputer, a gaming device, a wearable communication device (e.g., asmart watch or a pair of smart glasses), a mobile hotspot device, afixed wireless access device, customer premises equipment, an autonomousvehicle, or a similar type of device.

The RAN 110 may support, for example, a cellular radio access technology(RAT). The RAN 110 may include one or more base stations (e.g., basetransceiver stations, radio base stations, node Bs, eNodeBs (eNBs),gNodeBs (gNBs), base station subsystems, cellular sites, cellulartowers, access points, transmit receive points (TRPs), radio accessnodes, macrocell base stations, microcell base stations, picocell basestations, femtocell base stations, or similar types of devices) andother network entities that can support wireless communication for theuser device 105. The RAN 110 may transfer traffic between the userdevice 105 (e.g., using a cellular RAT), one or more base stations(e.g., using a wireless interface or a backhaul interface, such as awired backhaul interface), and/or the core network 115. The RAN 110 mayprovide one or more cells that cover geographic areas.

In some implementations, the RAN 110 may perform scheduling and/orresource management for the user device 105 covered by the RAN 110(e.g., the user device 105 covered by a cell provided by the RAN 110).In some implementations, the RAN 110 may be controlled or coordinated bya network controller, which may perform load balancing, network-levelconfiguration, and/or other operations. The network controller maycommunicate with the RAN 110 via a wireless or wireline backhaul. Insome implementations, the RAN 110 may include a network controller, aself-organizing network (SON) module or component, or a similar moduleor component. In other words, the RAN 110 may perform network control,scheduling, and/or network management functions (e.g., for uplink,downlink, and/or sidelink communications of the user device 105 coveredby the RAN 110).

Some implementations are described herein as being performed within along-term evolution (LTE) network for explanatory purposes. Someimplementations may be performed within a network that is not an LTEnetwork, such as a third generation (3G) network or a 5G network.

The environment 200 may include an evolved packet system (EPS) thatincludes an LTE network and/or an evolved packet core (EPC) (e.g., thecore network 115) that operate based on a third-generation partnershipproject (3GPP) wireless communication standard. The LTE network mayinclude a RAN that includes one or more RANs 110 that take the form ofevolved Node Bs (eNBs) via which the user device 105 communicates withthe EPC 115. The EPC 115 may include the P-CSCF 120, the MME 205, theSGW 210, the PGW 215, the PCRF 220, the OCS/CCF 225, the TAS 230, and/orthe I/S-CSCF 235 to enable the user device 105 to communicate with thenetwork 250 and/or an Internet protocol (IP) multimedia subsystem (IMS)core. The IMS core may include the HSS 240 and/or the AAA 245, and maymanage device registration and authentication, session initiation,and/or other operations associated with user devices 105. The HSS 240and/or the AAA 245 may reside in the EPC 115 and/or the IMS core.

The P-CSCF 120 includes one or more devices that manage all signalingfrom an end user to services and other networks. The P-CSCF 120 maycontrol both fixed and mobile IMSs, may allocate application servers,may establish emergency connections, and may control communication withother networks.

The MME 205 includes one or more devices, such as one or more serverdevices, capable of managing authentication, activation, deactivation,and/or mobility functions associated with the user device 105. In someimplementations, the MME 205 may perform operations relating toauthentication of the user device 105. Additionally, or alternatively,the MME 205 may facilitate the selection of a particular SGW 210 and/ora particular PGW 215 to provide traffic to and/or from the user device105. The MME 205 may perform operations associated with handing off theuser device 105 from a first RAN 110 to a second RAN 110 when the userdevice 105 is transitioning from a first cell associated with the firstRAN 110 to a second cell associated with the second RAN 110.Additionally, or alternatively, the MME 205 may select another MME (notpictured), to which the user device 105 should be handed off (e.g., whenthe user device 105 moves out of range of the MME 205).

The SGW 210 includes one or more devices capable of routing packets. Forexample, the SGW 210 may include one or more data processing and/ortraffic transfer devices, such as a gateway, a router, a modem, aswitch, a firewall, a network interface card (MC), a hub, a bridge, aserver device, an optical add/drop multiplexer (OADM), or any other typeof device that processes and/or transfers traffic. In someimplementations, the SGW 210 may aggregate traffic received from one ormore RANs 110 associated with the LTE network, and may send theaggregated traffic to the network 250 (e.g., via the PGW 215) and/orother network devices associated with the EPC 115 and/or the IMS core.The SGW 210 may receive traffic from the network 250 and/or othernetwork devices, and may send the received traffic to the user device105 via the RAN 110. Additionally, or alternatively, the SGW 210 mayperform operations associated with handing off the user device 105 toand/or from an LTE network.

The PGW 215 includes one or more devices capable of providingconnectivity for the user device 105 to external packet data networks(e.g., other than the depicted EPC 115 and/or the LTE network). Forexample, the PGW 215 may include one or more data processing and/ortraffic transfer devices, such as a gateway, a router, a modem, aswitch, a firewall, a MC, a hub, a bridge, a server device, an OADM, orany other type of device that processes and/or transfers traffic. Insome implementations, the PGW 215 may aggregate traffic received fromone or more SGWs 210, and may send the aggregated traffic to the network250. Additionally, or alternatively, the PGW 215 may receive trafficfrom the network 250, and may send the traffic to the user device 105via the SGW 210 and the RAN 110. The PGW 215 may record data usageinformation (e.g., byte usage), and may provide the data usageinformation to the AAA 245.

The PCRF 220 includes one or more devices, such as one or more serverdevices, capable of providing policy control decision and flow-basedcharging control functionalities. For example, the PCRF 220 may providenetwork control regarding service data flow detection, gating, and/orquality of service (QoS) and flow-based charging, among other examples.In some implementations, the PCRF 220 may determine how a certainservice data flow is to be treated, and may ensure that user planetraffic mapping and treatment is in accordance with a user subscriptionprofile.

The OCS/CCF 225 includes one or more devices, such as one or more serverdevices, that enable a cellular network service provider to chargecustomers (e.g., user devices 105), in real time, based on serviceusage. The OCS/CCF 225 may enable offline charging of network devices ofthe IMS core to report accounting information. The OCS/CCF 225 mayutilize the accounting information to construct and format a call detailrecording.

The TAS 230 includes one or more devices, such as one or more serverdevices, that provide telephony applications and additional multimediafunctions. The TAS 230 may be deployed in the core network 115 and/orthe IMS core, and may provide call control and media transformation,such as a soft switch or a media gateway. The TAS 230 may emulatecalling features, such as call forwarding, voicemail and conferencebridges, and may provide additional multimedia features, such as unifiedmessaging, video calling, and the integration of softphone clients onmultiple devices.

The I/S-CSCF 235 includes one or more devices that manage all signalingfrom an end user to services and other networks. The I/S-CSCF 235 maycontrol both fixed and mobile IMSs, may allocate application servers,may establish emergency connections, and may control communication withother networks.

The HSS 240 includes one or more devices, such as one or more serverdevices, capable of managing (e.g., receiving, generating, storing,processing, and/or providing) information associated with the userdevice 105. For example, the HSS 240 may manage subscription informationassociated with the user device 105, such as information that identifiesa subscriber profile of a user associated with the user device 105,information that identifies services and/or applications that areaccessible to the user device 105, location information associated withthe user device 105, a network identifier (e.g., a network address) thatidentifies the user device 105, information that identifies a treatmentof the user device 105 (e.g., quality of service information, a quantityof minutes allowed per time period, a quantity of data consumptionallowed per time period, etc.), and/or similar information. The HSS 240may provide this information to one or more other devices of theenvironment 200 to support the operations performed by those devices.

The AAA 245 includes one or more devices, such as one or more serverdevices, that perform authentication, authorization, and/or accountingoperations for communication sessions associated with the user device105. For example, the AAA 245 may perform authentication operations forthe user device 105 and/or a user of the user device 105 (e.g., usingone or more credentials), may control access, by the user device 105, toa service and/or an application (e.g., based on one or morerestrictions, such as time-of-day restrictions, location restrictions,single or multiple access restrictions, read/write restrictions, etc.),may track resources consumed by the user device 105 (e.g., a quantity ofvoice minutes consumed, a quantity of data consumed, etc.), and/or mayperform similar operations.

The network 250 includes one or more wired and/or wireless networks. Forexample, the network 250 may include a cellular network (e.g., a 5Gnetwork, an LTE network, a 3G network, a code division multiple access(CDMA) network, etc.), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a telephone network (e.g., the Public Switched Telephone Network(PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, and/or a combination of these orother types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2 . Furthermore, two or more devices shown in FIG. 3 maybe implemented within a single device, or a single device shown in FIG.2 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) of theenvironment 200 may perform one or more functions described as beingperformed by another set of devices of the environment 200.

FIG. 3 is a diagram of an example environment 300 in which systemsand/or methods described herein may be implemented. As shown in FIG. 3 ,the example environment 300 may include the user device 105, the RAN110, the core network 115, the OCS/CCF 225, the TAS 230, the HSS 240,and a data network 350. Details of the user device 105, the RAN 110, theOCS/CCF 225, the TAS 230, and the HSS 240 are provided elsewhere herein.Devices and/or networks of the example environment 300 may interconnectvia wired connections, wireless connections, or a combination of wiredand wireless connections.

In some implementations, the core network 115 may include an examplefunctional architecture in which systems and/or methods described hereinmay be implemented. For example, the core network 115 may include anexample architecture of a 5G next generation (NG) core network includedin a 5G wireless telecommunications system. While the examplearchitecture of the core network 115 shown in FIG. 3 may be an exampleof a service-based architecture, in some implementations, the corenetwork 115 may be implemented as a reference-point architecture and/ora 4G core network, among other examples.

As shown in FIG. 3 , the core network 115 may include a number offunctional elements. The functional elements may include, for example,the P-CSCF 120, the I/S-CSCF 235, a network slice selection function(NSSF) 305, an authentication server function (AUSF) 310, a unified datamanagement (UDM) component 315, a PCF 320, an application function (AF)325, an access and mobility management function (AMF) 330, a sessionmanagement function (SMF) 335, and/or a user plane function (UPF) 340.Details of the P-CSCF 120 and the I/S-CSCF 235 are provided elsewhereherein. The functional elements may be communicatively connected via amessage bus 345. Each of the functional elements shown in FIG. 3 isimplemented on one or more devices associated with a wirelesstelecommunications system. In some implementations, one or more of thefunctional elements may be implemented on physical devices, such as anaccess point, a base station, and/or a gateway. In some implementations,one or more of the functional elements may be implemented on a computingdevice of a cloud computing environment.

The NSSF 305 includes one or more devices that select network sliceinstances for the user device 105. By providing network slicing, theNSSF 305 allows an operator to deploy multiple substantially independentend-to-end networks potentially with the same infrastructure. In someimplementations, each slice may be customized for different services.

The AUSF 310 includes one or more devices that act as an authenticationserver and support the process of authenticating the user device 105 inthe wireless telecommunications system.

The UDM 315 includes one or more devices that store user data andprofiles in the wireless telecommunications system. The UDM 315 may beused for fixed access and/or mobile access in the core network 115.

The PCF 320 includes one or more devices that provide a policy frameworkthat incorporates network slicing, roaming, packet processing, and/ormobility management, among other examples.

The AF 325 includes one or more devices that support applicationinfluence on traffic routing, access to a network exposure function(NEF), and/or policy control, among other examples.

The AMF 330 includes one or more devices that act as a termination pointfor non-access stratum (NAS) signaling and/or mobility management, amongother examples.

The SMF 335 includes one or more devices that support the establishment,modification, and release of communication sessions in the wirelesstelecommunications system. For example, the SMF 335 may configuretraffic steering policies at the UPF 340 and/or may enforce userequipment IP address allocation and policies, among other examples.

The UPF 340 includes one or more devices that serve as an anchor pointfor intraRAT and/or interRAT mobility. The UPF 340 may apply rules topackets, such as rules pertaining to packet routing, traffic reporting,and/or handling user plane QoS, among other examples.

The message bus 345 represents a communication structure forcommunication among the functional elements. In other words, the messagebus 345 may permit communication between two or more functionalelements.

The data network 350 includes one or more wired and/or wireless datanetworks. For example, the data network 350 may include an IMS, a PLMN,a LAN, a WAN, a MAN, a private network such as a corporate intranet, anad hoc network, the Internet, a fiber optic-based network, a cloudcomputing network, a third party services network, an operator servicesnetwork, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 3 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 3 . Furthermore, two or more devices shown in FIG. 3 maybe implemented within a single device, or a single device shown in FIG.3 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) of theexample environment 300 may perform one or more functions described asbeing performed by another set of devices of the example environment300.

FIG. 4 is a diagram of example components of a device 400, which maycorrespond to the user device 105, the RAN 110, the P-CSCF 120, the MME205, the SGW 210, the PGW 215, the PCRF 220, the OCS/CCF 225, the TAS230, the I/S-CSCF 235, the HSS 240, the AAA 245, the NSSF 305, the AUSF310, the UDM 315, the PCF 320, the AF 325, the AMF 330, the SMF 335,and/or the UPF 340. In some implementations, the user device 105, theRAN 110, the P-CSCF 120, the MME 205, the SGW 210, the PGW 215, the PCRF220, the OCS/CCF 225, the TAS 230, the I/S-CSCF 235, the HSS 240, theAAA 245, the NSSF 305, the AUSF 310, the UDM 315, the PCF 320, the AF325, the AMF 330, the SMF 335, and/or the UPF 340 may include one ormore devices 400 and/or one or more components of the device 400. Asshown in FIG. 4 , the device 400 may include a bus 410, a processor 420,a memory 430, an input component 440, an output component 450, and acommunication component 460.

The bus 410 includes one or more components that enable wired and/orwireless communication among the components of the device 400. The bus410 may couple together two or more components of FIG. 4 , such as viaoperative coupling, communicative coupling, electronic coupling, and/orelectric coupling. The processor 420 includes a central processing unit,a graphics processing unit, a microprocessor, a controller, amicrocontroller, a digital signal processor, a field-programmable gatearray, an application-specific integrated circuit, and/or another typeof processing component. The processor 420 is implemented in hardware,firmware, or a combination of hardware and software. In someimplementations, the processor 420 includes one or more processorscapable of being programmed to perform one or more operations orprocesses described elsewhere herein.

The memory 430 includes volatile and/or nonvolatile memory. For example,the memory 430 may include random access memory (RAM), read only memory(ROM), a hard disk drive, and/or another type of memory (e.g., a flashmemory, a magnetic memory, and/or an optical memory). The memory 430 mayinclude internal memory (e.g., RAM, ROM, or a hard disk drive) and/orremovable memory (e.g., removable via a universal serial busconnection). The memory 430 may be a non-transitory computer-readablemedium. Memory 430 stores information, instructions, and/or software(e.g., one or more software applications) related to the operation ofthe device 400. In some implementations, the memory 430 includes one ormore memories that are coupled to one or more processors (e.g., theprocessor 420), such as via the bus 410.

The input component 440 enables the device 400 to receive input, such asuser input and/or sensed input. For example, the input component 440 mayinclude a touch screen, a keyboard, a keypad, a mouse, a button, amicrophone, a switch, a sensor, a global positioning system sensor, anaccelerometer, a gyroscope, and/or an actuator. The output component 450enables the device 400 to provide output, such as via a display, aspeaker, and/or a light-emitting diode. The communication component 460enables the device 400 to communicate with other devices via a wiredconnection and/or a wireless connection. For example, the communicationcomponent 460 may include a receiver, a transmitter, a transceiver, amodem, a network interface card, and/or an antenna.

The device 400 may perform one or more operations or processes describedherein. For example, a non-transitory computer-readable medium (e.g.,the memory 430) may store a set of instructions (e.g., one or moreinstructions or code) for execution by the processor 420. The processor420 may execute the set of instructions to perform one or moreoperations or processes described herein. In some implementations,execution of the set of instructions, by one or more processors 420,causes the one or more processors 420 and/or the device 400 to performone or more operations or processes described herein. In someimplementations, hardwired circuitry may be used instead of or incombination with the instructions to perform one or more operations orprocesses described herein. Additionally, or alternatively, theprocessor 420 may be configured to perform one or more operations orprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 4 are provided asan example. The device 400 may include additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 4 . Additionally, or alternatively, a set ofcomponents (e.g., one or more components) of the device 400 may performone or more functions described as being performed by another set ofcomponents of the device 400.

FIG. 5 is a flowchart of an example process 500 for network-basedidentification of priority services. In some implementations, one ormore process blocks of FIG. 5 may be performed by a network device(e.g., the P-CSCF 120). In some implementations, one or more processblocks of FIG. 5 may be performed by another device or a group ofdevices separate from or including the network device, such as an SGW(e.g., the SGW 210), a PCRF (e.g., the PCRF 220), an OCS/CCF (e.g., theOCS/CCF 225), a TAS (e.g., the TAS 230), an I/S-CSCF (e.g., the I/S-CSCF235), an HSS (e.g., the HSS 240), a PCF (e.g., the PCF 320), and/or aUPF (e.g., the UPF 340). Additionally, or alternatively, one or moreprocess blocks of FIG. 5 may be performed by one or more components ofthe device 400, such as the processor 420, the memory 430, the inputcomponent 440, the output component 450, and/or the communicationcomponent 460.

As shown in FIG. 5 , process 500 may include receiving, from a userdevice, a call associated with a telephone number and intended for apriority service associated with the telephone number (block 510). Forexample, the network device may receive, from a user device, a callassociated with a telephone number, as described above. In someimplementations, the call is intended for a priority service associatedwith the telephone number. In some implementations, the telephone numberis associated with one or more of a suicide hotline, a policedepartment, a fire department, a hospital, or a poison control service.

In some implementations, the network device is a P-CSCF. In someimplementations, the network device is associated with a fourthgeneration network or a fifth generation network.

As further shown in FIG. 5 , process 500 may include identifying thecall as a priority call based on the telephone number associated withthe call (block 520). For example, the network device may identify thecall as a priority call based on the telephone number associated withthe call, as described above. In some implementations, identifying thecall as a priority call based on the telephone number associated withthe call includes comparing digits of the telephone number with a listof telephone numbers associated with priority services, and identifyingthe call as a priority call based on the digits matching digits of atelephone number in the list of telephone numbers associated withpriority services.

As further shown in FIG. 5 , process 500 may include determining that anetwork overload condition exists (block 530). For example, the networkdevice may determine that a network overload condition exists, asdescribed above. In some implementations, the network overload conditionis due to one or more of a natural disaster, a man-made disaster, or aterrorist attack.

As further shown in FIG. 5 , process 500 may include associating apriority tag with the call based on identifying the call as a prioritycall (block 540). For example, the network device may associate apriority tag with the call based on identifying the call as a prioritycall, as described above. In some implementations, associating thepriority tag with the call includes associating a reservation priorityattribute-value pair (AVP) and a multimedia priority service AVP, as thepriority tag, with the call. In some implementations, associating thepriority tag with the call includes associating a session initiationprotocol resource priority header, as the priority tag, with the call.In some implementations, associating the priority tag with the callincludes associating a session priority attribute-value pair, as thepriority tag, with the call. In some implementations, the priority tagcauses one or more other network devices to modify the priority tagbased on one or more protocols associated with the one or more othernetwork devices.

As further shown in FIG. 5 , process 500 may include causing the call tobe provided preferential treatment based on the priority tag (block550). For example, the network device may cause the call to be providedpreferential treatment, while the call is transmitted for the priorityservice during the network overload condition, based on the prioritytag, as described above. In some implementations, causing the call to beprovided preferential treatment during the network overload conditionbased on the priority tag includes causing, based on the priority tag,one or more other network devices to identify the call as a prioritycall and to provide preferential treatment for the call during thenetwork overload condition. In some implementations, a connection isestablished between the user device and a priority service associatedwith the telephone number based on causing the call to be providedpreferential treatment during the network overload condition. In someimplementations, the one or more other network devices include one ormore of a UPF, a PCF, an I/S-CSCF, an HSS, a TAS, or an OCS/CCF.

In some implementations, process 500 includes storing, in a datastructure, a mapping of session priority AVP values associated withpriority services, session initiation protocol resource priority headersassociated with the priority services, and reservation priority AVPvalues associated with the priority services, and generating thepriority tag based on the mapping.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5 . Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Itwill be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, or thelike.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set. As used herein, aphrase referring to “at least one of” a list of items refers to anycombination of those items, including single members. As an example, “atleast one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c,and a-b-c, as well as any combination with multiple of the same item.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, or a combination of related and unrelateditems), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

In the preceding specification, various example embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

What is claimed is:
 1. A method, comprising: receiving, by a networkdevice and from a user device, a call associated with a telephonenumber, the call being intended for a priority service associated withthe telephone number; identifying, by the network device, the call as apriority call based on the telephone number associated with the call;determining, by the network device, that a network overload conditionexists; associating, by the network device, a priority tag with the callbased on identifying the call as a priority call; and causing, by thenetwork device, the call to be provided preferential treatment, whilethe call is transmitted for the priority service during the networkoverload condition, based on the priority tag.
 2. The method of claim 1,wherein the telephone number is associated with one or more of: asuicide hotline, a police department, a fire department, a hospital, ora poison control service.
 3. The method of claim 1, wherein causing thecall to be provided preferential treatment during the network overloadcondition based on the priority tag comprises: causing, based on thepriority tag, one or more other network devices to identify the call asa priority call and to provide preferential treatment for the callduring the network overload condition.
 4. The method of claim 3, whereinthe one or more other network devices include one or more of: user planefunction, a policy control function, a home subscriber server, aninterrogating or serving call session control function, a telephonyapplication server, or an online charging system/charging collectionfunction.
 5. The method of claim 1, wherein associating the priority tagwith the call comprises: associating a reservation priorityattribute-value pair (AVP) and a multimedia priority service AVP, as thepriority tag, with the call.
 6. The method of claim 1, whereinassociating the priority tag with the call comprises: associating asession initiation protocol resource priority header, as the prioritytag, with the call.
 7. The method of claim 1, wherein associating thepriority tag with the call comprises: associating a session priorityattribute-value pair, as the priority tag, with the call.
 8. A networkdevice, comprising: one or more processors configured to: receive, froma user device, a call associated with a telephone number and generatedduring a network overload condition; identify the call as a prioritycall based on the telephone number associated with the call; associate apriority tag with the call based on identifying the call as a prioritycall; and cause the call to be provided preferential treatment duringthe network overload condition throughout a network associated with thenetwork device and based on the priority tag.
 9. The network device ofclaim 8, wherein the one or more processors are further configured to:store, in a data structure, a mapping of session priorityattribute-value pair (AVP) values associated with priority services,session initiation protocol resource priority headers associated withthe priority services, and reservation priority AVP values associatedwith the priority services; and generating the priority tag based on themapping.
 10. The network device of claim 8, wherein the one or moreprocessors, to identify the call as a priority call based on thetelephone number associated with the call, are configured to: comparedigits of the telephone number with a list of telephone numbersassociated with priority services; and identify the call as a prioritycall based on the digits matching digits of a telephone number in thelist of telephone numbers associated with priority services.
 11. Thenetwork device of claim 8, wherein the network device is a proxy callsession control function.
 12. The network device of claim 8, wherein thenetwork device is associated with a fourth generation network or a fifthgeneration network.
 13. The network device of claim 8, wherein thepriority tag causes one or more other network devices to modify thepriority tag based on one or more protocols associated with the one ormore other network devices.
 14. The network device of claim 8, wherein aconnection is established between the user device and a priority serviceassociated with the telephone number based on causing the call to beprovided preferential treatment during the network overload condition.15. A non-transitory computer-readable medium storing a set ofinstructions, the set of instructions comprising: one or moreinstructions that, when executed by one or more processors of a networkdevice, cause the network device to: determine that a network overloadcondition exists in a network associated with the network device;receive, from a user device, a call associated with a telephone number;identify the call as a priority call based on the telephone numberassociated with the call; associate a priority tag with the call basedon identifying the call as a priority call; and cause the call to beprovided preferential treatment during the network overload conditionbased on the priority tag, wherein a connection is to be establishedbetween the user device and a priority service associated with thetelephone number based on causing the call to be provided preferentialtreatment during the network overload condition.
 16. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, that cause the network device to cause the call to beprovided preferential treatment during the network overload conditionbased on the priority tag, cause the network device to: cause, based onthe priority tag, one or more other network devices to identify the callas a priority call and to provide preferential treatment for the callduring the network overload condition.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, that cause the network device to associate the prioritytag with the call, cause the network device to: associate a reservationpriority attribute-value pair (AVP) and a multimedia priority serviceAVP, as the priority tag, with the call.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, that cause the network device to associate the prioritytag with the call, cause the network device to: associate a sessioninitiation protocol resource priority header, as the priority tag, withthe call.
 19. The non-transitory computer-readable medium of claim 15,wherein the one or more instructions further cause the network deviceto: store, in a data structure, a mapping of session priorityattribute-value pair (AVP) values associated with priority services,session initiation protocol resource priority headers associated withthe priority services, and reservation priority AVP values associatedwith the priority services, wherein the priority tag is generated basedon the mapping.
 20. The non-transitory computer-readable medium of claim15, wherein the one or more instructions, that cause the network deviceto identify the call as a priority call based on the telephone numberassociated with the call, cause the network device to: compare thetelephone number with a list of priority telephone numbers associatedwith priority services; and identify the call as a priority call basedon the telephone number matching a priority telephone number in the listof priority telephone numbers associated with priority services.